Event-based Action Objects
These Action Objects (AO) are user defined calculations scheduled to execute in an event-based (triggered) fashion. They are triggered to execute by an external event, or a user’s choice to trigger them in an external application.
All triggered Event-based Action Objects will display the following information:
Header |
Description |
Name |
The name given to the new Action Object. The default name is the name of the blueprint or data recipe file and the AO will be deployed with this name. If a name clash occurs, names will automatically be made unique. |
Status |
Waiting: The Action Object is waiting to be triggered to deploy the Action Object. Executing: The Action Object has been triggered, and is currently executing. |
Total executes |
The number of times the Action Object has executed. |
Failed executes |
The number of times the Action Object has failed to execute. |
Last status |
Success or failure: describes the status of the last execution. |
Last event |
The date and time of the last trigger event. |
Last start |
The start time of the last executed Action Object. |
Last end |
The end time of the last executed Action Object. |
Total time |
The duration of the execution. |
Average execution time |
The average duration of all the executions of that Action Object. |
Source |
Indicates who or what triggered the execution of the Action Object. |
Resource Gauges
Resource guages help you to understand the utilization of resources in your system. On the Event-based Action Objects window, you can view the current CPU, Memory utilization of your system, and Action Objects Utilization.
Understanding the Gauges
-
CPU gauge- This indicates the current utilization of your systems CPU in %.
-
Memory guage- This indicates the current utilization of your systems memory in %.
-
Utilization gauge- This indicates the actual number of action objects that are currently executing from the maximum concurrent limit that you configured.
Related topics: